Autonomous LTE-WLAN Interface Setup and Information Exchange

ABSTRACT

A node of a radio access network (RAN) receives, from a WLAN Termination (WT), an Extended Service Set Identifier (ESSID) and/or a Basic Service Set Identifier (BSSID) for one or more WLAN access points controlled by the WT. The node maintains a mapping between the ESSIDs and/or the BSSIDs and corresponding WLAN access points of the WT. Responsive to receiving a measurement report from a UE, the measurement report indicating an ESSID and/or a BSSID, the node associates the UE with a WLAN access point, based on said mapping. An interface may be established between the node and the WT.

TECHNICAL FIELD

The present invention generally relates to wireless communicationnetworks, and particularly relates to interfaces between cellular andWLAN networks.

BACKGROUND

The wireless local area network (WLAN) technology known as “Wi-Fi” hasbeen standardized by IEEE in the 802.11 series of specifications (i.e.,as “IEEE Standard for Information technology—Telecommunications andinformation exchange between systems. Local and metropolitan areanetworks—Specific requirements. Part 11: Wireless LAN Medium AccessControl (MAC) and Physical Layer (PHY) Specifications”). The IEEE 802.11specifications regulate the functions and operations of the Wi-Fi accesspoints (APs) or wireless terminals, collectively known as “stations” or“STA,” in the IEEE 802.11 standards, including the physical layerprotocols, Medium Access Control (MAC) layer protocols, and otheraspects needed to secure compatibility and inter-operability betweenaccess points and portable terminals. Wi-Fi is commonly used as awireless extension to fixed broadband access, e.g., in domesticenvironments and in so-called hotspots, like airports, train stationsand restaurants. Most current Wi-Fi/WLAN deployments are totallyseparate from mobile radio networks, and can be seen as“non-integrated,” from the perspective of the user terminal.

Recently, Wi-Fi has been subject to increased interest from cellularnetwork operators, who are studying the possibility of using Wi-Fi forpurposes beyond its conventional role as an extension to fixed broadbandaccess. These operators are responding to the ever-increasing marketdemands for wireless bandwidth, and are interested in using Wi-Fitechnology as an extension of, or alternative to, cellular radio accessnetwork technologies (RATs). Cellular operators that are currentlyserving mobile users with, for example, any of the technologiesstandardized by the 3rd-Generation Partnership Project (3GPP), includingthe radio-access technologies known as Long-Term Evolution (LTE),Universal Mobile Telecommunications System (UMTS)/Wideband Code-DivisionMultiple Access (WCDMA), and Global System for Mobile Communications(GSM), see Wi-Fi as a wireless technology that can provide goodadditional support for users of the operators' regular cellularnetworks.

In particular, 3GPP has studied ways to more tightly integrate LTE andWLAN, in particular for operator-deployed WLAN, so that traffic fromWLAN-enabled user equipments (UEs—3GPP terminology for an accessterminal) can be offloaded to WLAN from an eNodeB and vice versa. Inearly iterations of the standards for this integration, this tightenedintegration was achieved through semi-static policy setting, via AccessNetwork Discovery and Selection Function (ANDSF) and/or offloadthresholds broadcasted by the eNodeB (3GPP terminology for an evolvedbase station—also referred to as an “eNB”).

A 3GPP Rel-13 study item entitled Multi-RAT Joint Coordination has beenrecently started in 3GPP TSG RAN3 [3GPP TR 37.870]. The scope andrequirements for the Multi-RAT Joint Coordination SI have been furtherdefined in 3GPP working group meetings. In particular, for the 3GPP-WLANcoordination part, it has been agreed to focus on non-integrated3GPP/WLAN nodes (i.e., as so-called standalone eNodeB and standaloneAP), since integrated nodes are a matter of implementation.

Among the requirements of the study item [3GPP TR 37.870] is theinvestigation of potential enhancements of RAN interfaces and proceduresto support the joint operation among different RATs, including WLAN. Ithas also been agreed that i) coordination involving WLAN and 3GPP is thepriority of the study item, and ii) the statements on 3GPP/WLAN must becomplementary to RAN2 work [R3-141512]. This complement could beachieved by the specification of an interface between the E-UTRAN andWLAN, which may occur in future releases of the standards.

The main functionality so far envisioned for this interface, called sofar the “Xw interface,” is the support for traffic steering from LTE toWLAN via the reporting of different sets of information from WLAN to theeNodeB so that educated steering decisions can be taken. Also, 3GPP hasrecently approved a RAN2 work item on full network controlled 3GPP/WLANtraffic steering and aggregation [RP-150510, available atftp://ftp.3gpp.org/tsg_ran/TSG_RAN/TSGR_67/Docs/RP-150510.zip], and thusnew functionalities of the Xw interface can be envisioned.

As defined so far, the Xw interface is terminated in the eNodeB on theLTE network side, and in a logical node called WT (WLAN Termination) onthe WLAN side. The WT can physically reside in an AP or in an AC and isassumed to have IP connectivity to the relevant WLAN nodes. Possiblerealization of the protocol and architectural of the Xw interface aredepicted in FIGS. 1 and 2. Note that in the figures, the AP/AC has beenassigned the role of the WT for the sake of clarity, but the WT node canbe another node in the WLAN.

It is recognized herein that there are inefficiencies involved with Xwinterface setup. Accordingly, improved techniques are needed for settingup the Xw interface or other interface between a radio access networknode and a WT.

SUMMARY

Embodiments of the present invention comprise apparatuses and methodsfor correlating radio information reported by a user equipment (UE) withthe appropriate network addresses required to set up an interface, e.g.,an Xw interface, between a radio access network (RAN) node, such as aneNodeB, and a wireless local-area network termination (WT).

It is recognized herein that an eNodeB, or eNB, may benefit fromautonomously compiling and maintaining a mapping table that includes atleast the following information about its neighbor wireless local-areanetwork (WLAN) nodes: Transport Network Layer (TNL) address(es), a WT ID(a unique WT network node identifier), broadcasted Extended Service SetIdentifiers (ESSIDs), and broadcasted Basic Service Set Identifiers(BSSIDs). The Extended Service Set, of which the WLAN AP is a part,comprises one or multiple interconnected Basis Service Sets (WLAN APs),which appear as one logical entity to any UE/WLAN terminal connected toany of the underlying Basis Service Sets. An AP Location includes GPScoordinates or other location information related to the position of theWLAN AP. The TNL address(es) of the WT can be preconfigured in the eNBand/or looked up, e.g., using DNS queries. All other parameters can beexchanged and updated in the eNB via appropriate XwAP procedures. Inparticular, the eNB can query the WT about a newly found BSSID (asreported by a served WLAN-enabled UE). In the event that multiple APspertaining to a WT are configured to broadcast the same BSSID, the WTindicates this to the eNB with an appropriate information element (IE)in the relevant XwAP message(s) and the eNB takes this information intoaccount.

According to some embodiments of the presently disclosed techniques, amethod in a radio access network node of a wireless communicationnetwork includes receiving, from a WT, an ESSID and/or a BSSID for oneor more WLAN access points controlled by the WT. The method alsoincludes maintaining a mapping between the ESSIDs and/or the BSSIDs andcorresponding WLAN access points of the WT. The method further includes,responsive to receiving a measurement report from a UE, the measurementreport indicating an ESSID and/or a BSSID, associating the UE with aWLAN access point, based on said mapping. An interface, e.g., an Xwinterface, may be established between the radio access network node andthe WT that controls the associated WLAN access point.

According to some embodiments, a method at a WT controlling one or moreWLAN access points includes sending, to a radio access network node, anESSID and/or a BSSID for one or more WLAN access points controlled bythe WT. The method may also include responsive to receiving a requestfrom the radio access network node, establishing an interface, such asan Xw interface, to the radio access network node.

According to some embodiments, a radio access network node, configuredto maintain a mapping for establishing an interface between the radioaccess network node and a WT, is configured to receive, from the WT, anESSID and/or a BSSID for one or more WLAN access points controlled bythe WT. The radio access network node is further configured to maintaina mapping between the ESSIDs and/or the BSSIDs and corresponding WLANaccess points of the WT, and to associate the UE with a WLAN accesspoint, based on said mapping, responsive to receiving a measurementreport from UE, where the measurement report indicates an ESSID and/or aBSSID.

According to some embodiments, a WT, controlling one or more WLAN accesspoints and configured to send information for establishing an interfacebetween a radio access network node and the WT, is configured to send,to the radio access network node, an ESSID, and/or a BSSID, for one ormore WLAN access points controlled by the WT. The WT is also configuredto, responsive to receiving a request from the radio access networknode, establish the interface to the radio access network node. Thisinterface may be an Xw interface, for example.

Other embodiments include apparatus, computer program product, computerreadable medium and functional implementation embodiments that performthe operations of the method claims. Of course, the present invention isnot limited to the above features and advantages. Indeed, those skilledin the art will recognize additional features and advantages uponreading the following detailed description, and upon viewing theaccompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram of a protocol stack of an eNodeB, a UE and a WLANAP/AC.

FIG. 2 is a diagram illustrating an architecture involving an Xwinterface.

FIG. 3 illustrates a block diagram of a radio access network nodeconfigured to maintain a mapping for establishing an interface betweenthe radio access network node and a WT, according to some embodiments.

FIG. 4 illustrates a method in a radio access network node formaintaining a mapping for establishing an interface between the radioaccess network node and a WT, according to some embodiments.

FIG. 5 illustrates a block diagram of a WT configured to sendinformation to a radio access network node for establishing an interfacebetween the radio access network node and a WT, according to someembodiments.

FIG. 6 illustrates a method in a WT for sending information to a radioaccess network node for establishing an interface between the radioaccess network node and a WT, according to some embodiments.

FIG. 7 is a diagram illustrating an Xw interface between an eNodeB and aWT.

FIG. 8 is a diagram illustrating an Xw setup procedure, according tosome embodiments.

FIG. 9 illustrates a setup request message sent from an eNodeB to a WT,according to some embodiments.

FIG. 10 illustrates a setup response message sent from the WT to theeNodeB, according to some embodiments.

FIG. 11 illustrates a message sent from the WT to the eNodeB, accordingto some embodiments.

FIG. 12 is a diagram illustrating a configuration update procedure,according to some embodiments.

FIG. 13 illustrates a configuration update message sent from the WT tothe eNodeB, according to some embodiments.

FIG. 14 illustrates a configuration update acknowledge message sent fromthe eNodeB to the WT, according to some embodiments.

FIG. 15 is a diagram illustrating a configuration query procedure,according to some embodiments.

FIG. 16 illustrates a configuration query message sent from an eNodeB toa WT, according to some embodiments.

FIG. 17 illustrates an example functional implementation of a radioaccess network node configured to maintain a mapping for establishing aninterface between the radio access network node and a WT, according tosome embodiments.

FIG. 18 illustrates an example functional implementation of a WTconfigured to send information for establishing an interface between theWT and a radio access network node, according to some embodiments.

DETAILED DESCRIPTION

An interface between a WT and a radio access network node, such as anLTE eNB, can be set up following radio measurement reports by one ormore WLAN-enabled UEs to the serving eNB. For example, after the UEreports the relevant parameters for the WLAN(s) it detects (e.g. ESSID,BSSID, channel, signal strength, etc.), the eNB can try to set up theinterface with the appropriate WT(s). This interface may be referred toas an “Xw interface,” for example, but may have or come to have adifferent name, in some embodiments of the systems described herein.

Prior to the present disclosure, there is no way for the eNB tocorrelate the radio information reported by the UE with the appropriatenetwork address(es) required to set up the Xw interface. An eNB canalready be preconfigured with the ESSID(s) or BSSID(s) present in itsneighborhood, to be broadcasted in a System Information Block (SIB) asassistance data for UEs, but this does not contain network-levelinformation useful for setting up network interfaces. Such informationcould in principle be statically configured via Operations,Administration and Maintenance (OAM), but for high numbers of WLAN APsthat can potentially overlap with the eNB coverage, and given the factthat new WLAN APs can be easily deployed in areas with high capacitydemand, this seems infeasible.

An additional problem is the fact that multiple WLAN APs may beconfigured to broadcast the same BSSID (i.e., the AP MAC address)towards UEs/STAs, in order to make inter-AP mobility easier for some UEimplementations. Some additional logic will be required in the eNB toresolve this ambiguity, e.g., toward OAM and react appropriately.Moreover, unlike when compiling the Neighbor Relation Table (NRT) andsetting up the X2 interface to a neighbor eNB via ANR (AutomaticNeighbor Relations), the eNB cannot rely on the Mobility ManagementEntity (MME) to look up the network address of the neighbor AP, sincethat would require the MME to be either pre-configured with informationabout each and every WLAN AP, which would simply shift the burden ofpre-configuration to the MME, or to be aware of WLAN deployment, whichis not always the case and would increase its processing load.

The embodiments described herein provide apparatuses and methods forcorrelating radio information reported by the UE with the appropriatenetwork addresses required to set up the Xw interface. FIG. 3illustrates a diagram of a radio access network (RAN) node 30, such as abase station or an eNodeB, according to some embodiments. The RAN node30 provides an air interface to wireless devices, e.g., an LTE airinterface for downlink transmission and uplink reception, which isimplemented via antennas 34 and a transceiver circuit 36. Thetransceiver circuit 36 may include transmitter circuits, receivercircuits, and associated control circuits that are collectivelyconfigured to transmit and receive signals according to a radio accesstechnology, for the purposes of providing cellular communicationservices. According to various embodiments, cellular communicationservices may be operated according to any one or more of the 3GPPcellular standards, GSM, GPRS, WCDMA, HSDPA, LTE and LTE-Advanced. TheRAN node 30 may also include a communication interface circuit 38 forcommunicating with nodes in the core network such as a network node,other peer radio nodes, and/or other types of nodes in the network. TheRAN node 30 can communicate with one or more network nodes in a WLAN,such as one or more WLAN access points and/or WLAN access controllers.

The RAN node 30 also includes one or more processing circuits 32 thatare operatively associated with the communication interface circuit 38and transceiver circuit 36. The processing circuit 32 comprises one ormore digital processors 42, e.g., one or more microprocessors,microcontrollers, Digital Signal Processors or DSPs, Field ProgrammableGate Arrays or FPGAs, Complex Programmable Logic Devices or CPLDs,Application Specific Integrated Circuits or ASICs, or any mix thereof.More generally, the processing circuit 32 may comprise fixed circuitry,or programmable circuitry that is specially configured via the executionof program instructions implementing the functionality taught herein, ormay comprise some mix of fixed and programmed circuitry. The processor32 may be multi-core.

The processing circuit 32 also includes a memory 44. The memory 44, insome embodiments, stores one or more computer programs 46 and,optionally, configuration data 48. The memory 44 provides non-transitorystorage for the computer program 46 and it may comprise one or moretypes of computer-readable media, such as disk storage, solid-statememory storage, or any mix thereof. Here, “non-transitory” meanspermanent, semi-permanent, or at least temporarily persistent storageand encompasses both long-term storage in non-volatile memory andstorage in working memory, e.g., for program execution. By way ofnon-limiting example, the memory 44 comprises any one or more of SRAM,DRAM, EEPROM, and FLASH memory, which may be in the processing circuit32 and/or separate from the processing circuit 32. In general, thememory 44 comprises one or more types of computer-readable storage mediaproviding non-transitory storage of the computer program 46 and anyconfiguration data 48 used by the RAN node 30.

The processor 42 may execute a computer program 46 stored in the memory44 that configures the processor 42 to receive, from a WT, an ESSIDand/or a BSSID for one or more WLAN access points controlled by the WT.The processor 42 is also configured to maintain a mapping between theESSIDs and/or the BSSIDs and corresponding WLAN access points of the WT.For example, the ESSIDs may be mapped to corresponding WLAN accesspoints. In an alternative example, the BSSIDs may be mapped tocorresponding WLAN access points. In another example, both the ESSIDsand the BSSIDs may be mapped to corresponding WLAN access points. Theprocessor 42 is configured to, responsive to receiving a measurementreport from a UE (the measurement report indicating an ESSID and/or aBSSID), associate the UE with a WLAN access point, based on the mapping.This structure and functionality may be referred to as interfacecircuitry 40 in the processing circuit 32.

The interface circuitry 40 is configured to perform a method, such asmethod 400 of FIG. 4, according to some embodiments. The method 400includes receiving, from a WT, an ESSID and/or a BSSID for one or moreWLAN access points controlled by the WT (block 402). The method 400includes maintaining a mapping between the ESSIDs and/or the BSSIDs andcorresponding WLAN access points of the WT (block 404). The method 400also includes, responsive to receiving a measurement report from a UE(the measurement report indicating an ESSID and/or a BSSID), associatingthe UE with a WLAN access point, based on the mapping (block 406). Themethod may include establishing an Xw interface or similar interface(block 408).

In some cases, the method 400 includes identifying a TNL addresscorresponding to the WT and associating the TNL address to the WT in themapping. The TNL addresses for relevant WTs may be preconfigured in theRAN node. The method 400 may also include performing a Domain NameSystem, DNS, query to obtain TNL addresses for relevant WTs. ESSIDsand/or BSSIDs may also be requested from the WT.

FIG. 5 illustrates a diagram of a WT 70, according to some embodiments.The WT controls any number of access points (APs) and may function as orreside in an AP-AC, or another node. In some embodiments, such an AP orAC may include components and functionality as illustrated in FIG. 5.

The WT 70 can provide an air interface to wireless devices, e.g., Wi-Fior IEEE 802.11 standards, which is implemented via antennas 74 and atransceiver circuit 76. The transceiver circuit 76 may includetransmitter circuits, receiver circuits, and associated control circuitsthat are collectively configured to transmit and receive signalsaccording to WLAN technologies. The WT 70 may also include acommunication interface circuit 78 for communicating with nodes in thecore network and/or other types of nodes in the network.

The WT 70 also includes one or more processing circuits 72 that areoperatively associated with the communication interface circuit 78 andtransceiver circuit 76. The processing circuit 72 comprises one or moredigital processors 82, e.g., one or more microprocessors,microcontrollers, DSPs, FPGAs, CPLDs, ASICs, or any mix thereof. Moregenerally, the processing circuit 72 may comprise fixed circuitry, orprogrammable circuitry that is specially configured via the execution ofprogram instructions implementing the functionality taught herein, ormay comprise some mix of fixed and programmed circuitry. The processor72 may be multi-core.

The processing circuit 72 also includes a memory 84. The memory 84, insome embodiments, stores one or more computer programs 86 and,optionally, configuration data 88. The memory 84 provides non-transitorystorage for the computer program 86 and it may comprise one or moretypes of computer-readable media, such as disk storage, solid-statememory storage, or any mix thereof. By way of non-limiting example, thememory 84 comprises any one or more of SRAM, DRAM, EEPROM, and FLASHmemory, which may be in the processing circuit 72 and/or separate fromthe processing circuit 72. In general, the memory 84 comprises one ormore types of computer-readable storage media providing non-transitorystorage of the computer program 86 and any configuration data 88 used bythe AP 70.

The processor 82 may execute a computer program 86 stored in the memory84 that configures the processor 82 to send, to a radio access networknode, an ESSID and/or a BSSID for one or more WLAN access pointscontrolled by the WT. The processor 82 is also configured to, responsiveto receiving a request from the radio access network node, establish aninterface, e.g., an Xw interface, to the radio access network node. Thisstructure and functionality may be referred to as interface circuitry 80in the processing circuit 72.

The interface circuitry 80 is configured to perform a method, such asmethod 600 of FIG. 6, according to some embodiments. The method 600includes sending, to a radio access network node, an ESSID and/or aBSSID for one or more WLAN access points controlled by the WT (block602). The method 600 also includes, responsive to receiving a requestfrom the radio access network node, establishing an interface, such asan Xw interface, to the radio access network node (block 604).

FIG. 7 shows a basic diagram of an Xw interface 100 between a RAN node30, such as eNodeB 30, and a WT 70. Although eNodeB 30 is used torepresent a RAN node 30, embodiments of the RAN node 30 are not limitedto eNodeBs and may include other cellular RAN nodes. According tovarious embodiments, the WT 70 and the eNodeB node 30 may request,respond to and coordinate with each other to assist the eNodeB 30 inidentifying the WT 70 and APs associated with UE measurements. WT 70 andeNodeB 30 may establish an interface, such as an Xw interface 100,between the WT 70 and the eNodeB 30. The eNodeB 30 need not rely on anMME 90 to look up the network address of a neighbor AP.

In previous Xw interface setup procedures, the assumption was that thereis a direct interface between an eNodeB and a WLAN AP. Variousembodiments described herein involve the case of the Xw interfacesetup/(re)configuration when there is a WT that iscontrolling/interfacing several APs towards the eNodeB.

In some embodiments, the WT 70 signals to the RAN node 30 its WT ID,ESSID(s) and/or BSSID(s) of the WLAN APs under the control of the WT 70during Xw interface setup. This can be achieved using the procedureshown in FIG. 8, initiated by the eNodeB 30. For example, the method 400may include sending a setup request message to the WT 70. This is shownby Xw SETUP REQUEST message 802 in FIG. 8. The Xw SETUP REQUEST message202 includes an interface access point transaction identifier thatuniquely identifies the setup transaction and a unique global networkaccess node identifier that identifies the RAN node 30 with a RAN. Theseidentifiers may be, for example, a XwAP Transaction ID and a Global eNBID, respectively. The XWAP Transaction ID is a parameter that uniquelyidentifies the setup transaction. This can be used to distinguish such atransaction from other similar procedures involving other eNodeBs. TheGlobal eNB ID is a parameter that uniquely identifies an eNodeB withinthe LTE RAN.

A sample tabular structure for the Xw SETUP REQUEST messages 802 isshown in FIG. 9. The BSSID broadcasted by each AP is included in theServed AP Information IE, together with radio-related information(frequency band, channel, protocol version) useful for setting up therelation. The XwAP Transaction ID and Criticality Diagnostics IEs areshown in the table of FIG. 9. The Global eNB ID is also shown in thetable of FIG. 9. The TNL address(es) of the WT can be preconfigured inthe eNodeB 30 via OAM, or looked up by the eNodeB 30 via DNS queriesaccording to a configuration.

Upon reception of the Xw SETUP REQUEST message 802, the WT 70 shalldeduce that an Xw interface has to be setup and that it should respondwith the Xw SETUP RESPONSE message 804, which acknowledges acceptance ofXw establishment. Method 600 may include sending a setup responsemessage, such as the Xw SETUP RESPONSE message 804, to the RAN node 30responsive to receiving the request.

Optionally, the Xw SETUP REQUEST message 802 may contain a list of cellsserved by the sending eNodeB 30 and a list of neighboring cells for thesending eNodeB 30. This information may be taken into account by the WT70 in order to create neighbor relations between each served AP and thecells served by the eNodeB 30 or the cells neighboring the eNodeB 30.

As shown in FIG. 10, the Xw SETUP RESPONSE message 804 contains the sameXWAP Transaction ID specified in the Xw SETUP REQUEST message 802. TheXw SETUP RESPONSE message 804 contains a WT ID, which is a parameteruniquely identifying the WT within the Wi-Fi access network. The XwSETUP RESPONSE message 804 may contain a list of ESSIDs which may beused by APs associated to or served by the WT 70. This information maybe used by the eNodeB 30 when receiving UE measurements reporting one ormore ESSIDs. The eNodeB 30 may then be able to identify the correct WT70 for such reported APs.

The Xw SETUP RESPONSE message 804 may also contain a list of ServedAccess Point information, which may include for example a list of BSSIDsused by the APs associated to or served by the WT 70. As describedabove, this information may be useful when UEs report AP measurements.The measurements may include BSSIDs, which the eNodeB 30 would be ableto associate to APs connected to the WT 70 with which the Xw interfacehas been setup. These lists are shown in the table of FIG. 10.

FIG. 10 also shows a second table with parameters maxESSIDperWT and themaxAPsperWT. The parameter maxESSIDperWT indicates the maximum number ofESSIDs broadcasted by the APs served by the WT 70, while max APsperWTindicates the maximum number of WLAN APs that can be served by a WT 70.

It should be noted that in the above and subsequent messages, it hasbeen shown that the ESSIDs and the BSS ID s can be communicatedindependently (e.g., the Broadcasted ESSIDs and Served Access points arenot related in the message). For example, given an ESSID1 and an ESSID2,and given that there are four APs, BSSID1 to BSSID4, the first twobelonging to ESSID1 and the rest belonging to ESSID2, it might bebeneficial to have this information as well. So, an alternative to theabove message can be used to include this aspect, as shown in FIG. 11.For example, the range of the Served Access Points is limited by themaxAPsperESSID parameter in FIG. 11 rather than the maxAPsperWTparameter shown in the tables of FIG. 10. The maxAPsperESSID parameterindicates the maximum number of WLAN APs that can be under one ESSID, asshown by the second table of FIG. 11.

The eNodeB 30 uses the information received in the Xw SETUP RESPONSEmessage 804 to populate and maintain its internal WNRT (WT NeighborhoodRelationship Table). The WNRT is a table that includes at least thefollowing information for each WT: WT ID, TNL address(es), BroadcastedESSID(s), Broadcasted BSSID(s). The WNRT may include other parameterssuch as an “Xw no removal” flag, indicating whether an Xw interface mayor may not be removed.

In some embodiments, the WT 70 signals to the eNodeB 30 any changes inits configuration using the WT Configuration Update procedure, shown inFIG. 12. For example, method 400 may include sending a configurationupdate message to the WT 70, where the configuration update messagecomprises a list of cells served by the RAN node 30 and a list ofneighboring cells for the RAN 30. An example configuration updatemessage is shown by the WT CONFIGURATION UPDATE message 1202 in FIG. 12.Sample tabular structures for the messages are shown in FIG. 13. Similarto the case of WT SETUP RESPONSE message 804, ESSID to BSSID groupinginfo can also be included. The example table in FIG. 13 includes a listof new ESSIDs to be broadcasted by the APs that are served by the WT 70(to be added). The table also includes a list of ESSIDs to no longer bebroadcasted by the APs served by the WT 70 (to be deleted) Likewise, thetable includes a list of new Service Access Points served by the WT 70(to be added) and a list of Service Access Points to no longer be servedby the WT 70 (to be deleted). Served AP information and CriticalityDiagnostics is also included in the table.

Although the basic use of the WT CONFIGURATION UPDATE message 1202 is toupdate the eNodeB 30 about changing conditions in the WT 70configuration or to respond to an eNodeB 30 query, the WT configurationupdate message 1202 can also be used to address limitations of the valueof the maxESSIDperWT and the maxAPsperWT. If these are not sufficient toinclude all the APs that need to be communicated during the Xw SETUPRESPONSE message 804, the WT 70 can send multiple WT CONFIGURATIONUPDATE messages 1202 towards the eNodeB 30 to communicate all therequired information.

The WT CONFIGURATION UPDATE ACKNOWLEDGE message 1204 is sent by aneNodeB 30 to a WT 70 to acknowledge update of information for a TNLassociation. FIG. 14 illustrates an example WT CONFIGURATION UPDATEACKNOWLEDGE message 1204. The table of FIG. 14 includes a Message Type,XWAP Transaction ID and Criticality Diagnostics. People skilled in theart will appreciate that the WT Configuration Update procedure may berealized as a Class 2 procedure (i.e., unacknowledged by the receivingeNodeB 30). In this case, there is a trade-off between a simplerimplementation and a less reliable system behavior.

In a way similar to the WT Configuration Update procedure, someembodiments include specifying an eNB Configuration Update procedurefrom the eNodeB 30 to the WT 70, where the eNodeB 30 may updateinformation about its own configuration such as updates of the list ofserved cells or updates of the list of neighboring cells.

In some embodiments, a procedure flow may include a WLAN-enabled UEdetecting a WLAN and reporting its BSSID, ESSID and radio parameters toits serving eNodeB 30. The eNodeB 30 looks up the BSSID and ESSID in itsinternal WNRT (WT Neighborhood Relationship Table). If the reportedESSID and BSSID are already present in the WNRT, the eNodeB 30 logicallyassociates the UE with the WT ID corresponding to the reported ESSID andBSSID. When the ESSID and/or BSSID are not present, the eNodeB 30queries the known WT(s) for the discovered ESSID and/or BSSID using theWT Configuration Query procedure, shown in FIG. 15.

A sample tabular structure for the message is shown in FIG. 16. Thetable includes a Message Type and a XWAP Transaction ID. The table alsoincludes a list of queried ESSIDs and a list of queried BSSIDs. Thesecond table of FIG. 16 includes the maximum number of queried ESSIDs(maxESSIDs) and the maximum number of queried BSSIDs (maxBSSIDs).

The WT CONFIGURATION QUERY message 1502 is sent by an eNodeB 30 to a WT70 to query about newly discovered ESSID(s) and/or BSSID(s). If therequested ESSID(s) and/or BSSID(s) belong to the queried WT 70, thequeried WT 70 initiates the WT Configuration Update procedure toward theeNodeB 30 signaling its complete updated configuration.

People skilled in the art will appreciate that the WT ConfigurationQuery procedure may be realized as a Class 2 procedure (i.e., may beunacknowledged by the receiving WT 70). This way, the eNodeB 30 candeduce that not receiving a WT CONFIGURATION UPDATE message 1202 from aWT 70 means that the WT 70 is not serving any APs that are broadcastingthe included ESSID and BSSIDs. This can reduce unnecessary signaling inthe cases where the eNodeB 30 has connectivity to different WTs (e.g.,several WLAN networks with the coverage area of the eNodeB 30).

It should be noted that since one WT can control/interface hundreds oreven thousands of APs, only a fraction of those may berelevant/neighboring to a certain eNodeB. Therefore, instead of givingthe information about all of its WLAN APs to all of the eNodeBs, the WTmay only give information about some or all of the ESSID(s) and some ofthe BSSID(s) that its APs support during the initial Xw setup. Then,each eNodeB can query for information about individual APs that arebeing discovered by the UEs that it is serving via subsequent WTconfiguration procedures. If the ESSID to WT association is known butnot the AP BSSID, the query information may be sent only to the WTassociated to that ESSID.

In some embodiments, the method 600 includes sending a parameter to a UEto assist the UE in identifying the WLAN AP. For example, the WLAN APcommunicates to the UE a locally unique parameter (AP UniqueIdentifier), which the UE can later communicate as part of the WLANmeasurement report to the eNodeB 30. This parameter can help the eNodeB30 distinguish between APs that broadcast the same ESSID and BSSID (inorder to improve inter-AP mobility). This parameter can be communicatedeither via broadcast (e.g., Beacon frame, Fast Initial Link Discovery(FILS) Discovery frame, etc.) or unicast (e.g., Probe Response frames,Association or Reassociation Response frames, Authentication Responseframes, Access Network Query Protocol (ANQP) message exchange, etc.)signaling. The AP Unique Identifier can be communicated as a newlydefined information element or as a vendor-specific information element.The value of the element (i.e., the unique number) can either be drawnby the AP itself, or could be allocated by a WT.

It is observed that LTE-WLAN aggregation functionality may be similar tothe Dual Connectivity (DC) functionality specified in Rel-12. DCfunctionality builds upon the capability to autonomously set up an X2interface between the Master eNodeB (MeNB) and the Secondary eNodeB(SeNB) as needed, in order to exchange (among other things) thesignaling needed for the DC functionality. Such capability may also beneeded between the eNB and the WT in order to build similarfunctionality between LTE and WLAN. It is also observed that in order toprovide the full flexibility needed for LTE-WLAN aggregation, supportfor autonomous setup and information exchange over Xw needs to bespecified. Due to the specific eNB-WLAN architecture, it may not bepossible to completely reuse the same paradigm specified for the X2interface.

According to some embodiments, the Xw interface can be set up followingradio measurement reports by one or more WLAN-enabled UEs to the servingeNodeB 30. For example, after the UE reports the relevant parameters forthe WLAN(s) it picks up (e.g., ESSID, BSSID, channel, signal strength,etc.), the eNodeB 30 can try to set up the interface with theappropriate WT(s). This may be more straightforward than having the WT70 initiate interface setup towards the eNodeB 30, since it isbeneficial to be able to trigger it as needed from UE measurements.

Previously, there was no method for the eNodeB 30 to correlate the radioinformation reported by the UE with the appropriate TNL address(es)required to set up the Xw interface. An eNodeB 30 can already bepreconfigured with the ESSID(s) or BSSID(s) present in its neighborhood,to be broadcasted in a SIB as assistance data for UEs, but this does notcontain network-level information useful for setting up networkinterfaces.

It is observed that if the MME 90 was made aware of the WLAN deployment,the SlAP self-organizing network (SON) configuration transfer could beextended so that the eNodeB 30 can look up WT addresses through the MME90. But the only way the MME 90 would know the TNL address of a WT 70 isthrough local configuration, so this would merely shift the burden ofconfiguration to the MME 90. This would also be inconsistent with theobjectives of both the Multi-RAT Joint Coordination Study Item and theLTE-WLAN Aggregation Work Item, since it would impact the Evolved PacketCore (EPC). In addition, this would introduce an exception in thecurrent behavior which states that the MME 90 does not interpret the SONConfiguration Transfer IE but transparently transfer it to thedestination.

According to some embodiments, in reply to the Xw SETUP REQUEST message802 from the eNodeB 30, the WT 70 signals the list of broadcasted ESSIDsand the APs it supports, with their BSSIDs, included with anyradio-related information necessary to set up the relation. A WTconfiguration update procedure would be beneficial to enable a WT 70 tosignal a change of configuration to the eNodeB(s) with which it has arelation.

According to some embodiments, a WT configuration update procedureenables a WT 70 to signal configuration changes to eNodeBs 30. This mayinclude a “query” mechanism for an eNodeB 30 toward the WT 70. This canhelp in case, for example, a UE picks up an ESSID or BSSID that theeNodeB 30 does not know about, but which for some reason has not beenpropagated to the eNodeB 30. Such a potential WT configuration requestquery could be sent to the WT 70 with a list of queriedESSID(s)/BSSID(s). If the ESSID(s)/BSSID(s) present in the list belongto the queried WT 70, it can initiate a WT configuration update towardthe eNodeB 30 signaling its complete updated configuration.

FIG. 17 illustrates an example functional module or circuit architectureas may be implemented in the RAN node 30, e.g., based on the interfacecircuitry 40. The illustrated embodiment at least functionally includesa receiving module 1702 for receiving, from a WT 70, an ESSID and/or aBSSID for one or more WLAN access points controlled by the WT 70. Theembodiment includes a maintaining module 1704 for maintaining a mappingbetween the ESSIDs and/or the BSSIDs and corresponding WLAN accesspoints of the WT 70. The embodiment includes an associating module 1706for, responsive to receiving a measurement report from a UE, themeasurement report indicating an ESSID and/or a BSSID, associating theUE with a WLAN access point, based on the mapping. The embodiment mayalso include an establishing module 1708 for establishing an Xwinterface 100 between the RAN node 30 and the WT 70 that controls theassociated WLAN access point.

FIG. 18 illustrates an example functional module or circuit architectureas may be implemented in the WT 70, e.g., based on the processingcircuitry 80. The illustrated embodiment at least functionally includesa sending module 1802 for sending, to a RAN node 30, an ESSID and/or aBSSID for one or more WLAN access points controlled by the WT 70. Theembodiment may also include an establishing module 1804, for, responsiveto receiving a request from the RAN node 30, establishing an Xwinterface 100 to the RAN node 30.

With the embodiments described herein, it is possible to autonomouslyset up and maintain a set of neighbor relationships between one or moreeNodeBs and one or more WLAN nodes, minimizing OAM actions and enablingthe network to optimize itself according to traffic and UE mobility. Itis also possible to detect on the eNodeB side potentialmisconfigurations in the WLAN nodes and report them to OAM so thatappropriate action can be taken. It is also possible to speed up thedeployment of new WLAN APs in areas demanding higher capacity.

Notably, modifications and other embodiments of the disclosedinvention(s) will come to mind to one skilled in the art having thebenefit of the teachings presented in the foregoing descriptions and theassociated drawings. Therefore, it is to be understood that theinvention(s) is/are not to be limited to the specific embodimentsdisclosed and that modifications and other embodiments are intended tobe included within the scope of this disclosure. Although specific termsmay be employed herein, they are used in a generic and descriptive senseonly and not for purposes of limitation.

What is claimed is:
 1. A method, in a radio access network node of awireless communication network, the method comprising: receiving, from aWireless Local-Area Network Termination (WT), an Extended Service SetIdentifier (ESSID) and/or a Basic Service Set Identifier (BSSID) for oneor more Wireless Local-Area Network (WLAN) access points controlled bythe WT; maintaining a mapping between the ESSIDs and/or the BSSIDs andcorresponding WLAN access points of the WT; and responsive to receivinga measurement report from a user equipment (UE), the measurement reportindicating an ESSID and/or a BSSID, associating the UE with a WLANaccess point, based on said mapping.
 2. The method of claim 1, furthercomprising establishing an interface between the radio access networknode and the WT that controls the associated WLAN access point.
 3. Themethod of claim 1, further comprising identifying a Transport NetworkLayer (TNL) address corresponding to the WT and associating the TNLaddress to the WT in the mapping.
 4. The method of claim 3, wherein TNLaddresses for one or more WTs neighboring the radio access network nodeare preconfigured in the radio access network node.
 5. The method ofclaim 3, further comprising performing a Domain Name System (DNS) queryto obtain TNL addresses for the one or more WTs neighboring the radioaccess network node.
 6. The method of claim 1, further comprisingrequesting the ESSIDs and/or the BSSIDs from the WT.
 7. The method ofclaim 1, further comprising sending a setup request message to the WT,wherein the setup request message comprises an interface access pointtransaction identifier that uniquely identifies the setup transactionand a unique global network access node identifier that identifies theradio access network node with a radio access network.
 8. The method ofclaim 1, further comprising sending a configuration update message tothe WT, wherein the configuration update message comprises a list ofcells served by the radio access network node and a list of neighboringcells for the radio access network node.
 9. A method, at a wirelesslocal area network termination (WT) controlling one or more wirelesslocal area network (WLAN) access points, the method comprising: sending,to a radio access network node, an Extended Service Set Identifier(ESSID) and/or a Basic Service Set Identifier (BSSID) for one or moreWLAN access points controlled by the WT; and responsive to receiving arequest from the radio access network node, establishing an interface tothe radio access network node.
 10. The method of claim 9, furthercomprising sending a setup response message to the radio access networknode responsive to receiving the request, wherein the setup responsemessage comprises a WT identifier.
 11. The method of claim 10, whereinthe setup response message comprises the ESSID and/or the BSSID.
 12. Themethod of claim 9, further comprising sending a parameter to a userequipment to assist the user equipment in identifying the WLAN accesspoint.
 13. A radio access network node configured to maintain a mappingfor establishing an interface between the radio access network node anda wireless local area network termination (WT), the radio access networknode comprising a processing circuit configured to: receive, from theWT, an Extended Service Set Identifier (ESSID) and/or a Basic ServiceSet Identifier (BSSID) for one or more wireless local area network(WLAN) access points controlled by the WT; maintain a mapping betweenthe ESSIDs and/or the BSSIDs and corresponding WLAN access points of theWT; and responsive to receiving a measurement report from a userequipment (UE) the measurement report indicating an ESSID and/or aBSSID, associate the UE with a WLAN access point, based on said mapping.14. The radio access network node of claim 13, wherein the processingcircuit is further configured to establish an interface between theradio access network node and the WT that controls the associated WLANaccess point.
 15. The radio access network node of claim 13, wherein theprocessing circuit is further configured to identify a Transport NetworkLayer (TNL) address corresponding to the WT and to associate the TNLaddress to the WT in the mapping.
 16. The radio access network node ofclaim 15, wherein TNL addresses for one or more WTs neighboring theradio access network node are preconfigured in the radio access networknode.
 17. The radio access network node of claim 15, wherein theprocessing circuit is further configured to perform a Domain Name System(DNS) query to obtain TNL addresses for the one or more WTs neighboringthe radio access network node.
 18. The radio access network node ofclaim 13, wherein the processing circuit is further configured torequest the ESSIDs and/or the BSSIDs from the WT.
 19. The radio accessnetwork node of claim 13, wherein the processing circuit is furtherconfigured to send a setup request message to the WT, and wherein thesetup request message comprises an interface access point transactionidentifier that uniquely identifies the setup transaction and a uniqueglobal network access node identifier that identifies the radio accessnetwork node with a radio access network.
 20. The radio access networknode of claim 13, wherein the processing circuit is further configuredto send a configuration update message to the WT, wherein theconfiguration update message comprises a list of cells served by theradio access network node and a list of neighboring cells for the radioaccess network node.